SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
PHP

PHP static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your PHP code

  • All rules 273
  • Vulnerability42
  • Bug51
  • Security Hotspot34
  • Code Smell146
 
Tags
    Impact
      Clean code attribute
        1. Hard-coded secrets are security-sensitive

           Security Hotspot
        2. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        3. Allowing unfiltered HTML content in WordPress is security-sensitive

           Security Hotspot
        4. Allowing unauthenticated database repair in WordPress is security-sensitive

           Security Hotspot
        5. Allowing all external requests from a WordPress server is security-sensitive

           Security Hotspot
        6. Disabling automatic updates is security-sensitive

           Security Hotspot
        7. WordPress theme and plugin editors are security-sensitive

           Security Hotspot
        8. Allowing requests with excessive content length is security-sensitive

           Security Hotspot
        9. Using clear-text protocols is security-sensitive

           Security Hotspot
        10. Manual generation of session ID is security-sensitive

           Security Hotspot
        11. Having a permissive Cross-Origin Resource Sharing policy is security-sensitive

           Security Hotspot
        12. Expanding archive files without controlling resource consumption is security-sensitive

           Security Hotspot
        13. Controlling permissions is security-sensitive

           Security Hotspot
        14. Reading the Standard Input is security-sensitive

           Security Hotspot
        15. Signaling processes is security-sensitive

           Security Hotspot
        16. Using command line arguments is security-sensitive

           Security Hotspot
        17. Using Sockets is security-sensitive

           Security Hotspot
        18. Configuring loggers is security-sensitive

           Security Hotspot
        19. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        20. Encrypting data is security-sensitive

           Security Hotspot
        21. Using regular expressions is security-sensitive

           Security Hotspot
        22. Deserializing objects from an untrusted source is security-sensitive

           Security Hotspot
        23. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        24. Disabling CSRF protections is security-sensitive

           Security Hotspot
        25. Creating cookies with broadly defined "domain" flags is security-sensitive

           Security Hotspot
        26. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        27. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        28. Writing cookies is security-sensitive

           Security Hotspot
        29. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        30. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        31. Formatting SQL queries is security-sensitive

           Security Hotspot
        32. Hard-coded credentials are security-sensitive

           Security Hotspot
        33. Dynamically executing code is security-sensitive

           Security Hotspot
        34. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Creating cookies without the "HttpOnly" flag is security-sensitive

        intentionality - complete
        security
        Security Hotspot
        • cwe
        • privacy

        When a cookie is configured with the HttpOnly attribute set to true, the browser guaranties that no client-side script will be able to read it. In most cases, when a cookie is created, the default value of HttpOnly is false and it’s up to the developer to decide whether or not the content of the cookie can be read by the client-side script. As a majority of Cross-Site Scripting (XSS) attacks target the theft of session-cookies, the HttpOnly attribute can help to reduce their impact as it won’t be possible to exploit the XSS vulnerability to steal session-cookies.

        Ask Yourself Whether

        • the cookie is sensitive, used to authenticate the user, for instance a session-cookie
        • the HttpOnly attribute offer an additional protection (not the case for an XSRF-TOKEN cookie / CSRF token for example)

        There is a risk if you answered yes to any of those questions.

        Recommended Secure Coding Practices

        • By default the HttpOnly flag should be set to true for most of the cookies and it’s mandatory for session / sensitive-security cookies.

        Sensitive Code Example

        In php.ini you can specify the flags for the session cookie which is security-sensitive:

        session.cookie_httponly = 0;  // Sensitive: this sensitive session cookie is created with the httponly flag set to false and so it can be stolen easily in case of XSS vulnerability
        

        Same thing in PHP code:

        session_set_cookie_params($lifetime, $path, $domain, true, false);  // Sensitive: this sensitive session cookie is created with the httponly flag (the fifth argument) set to false and so it can be stolen easily in case of XSS vulnerability
        

        If you create a custom security-sensitive cookie in your PHP code:

        $value = "sensitive data";
        setcookie($name, $value, $expire, $path, $domain, true, false); // Sensitive: this sensitive cookie is created with the httponly flag (the seventh argument) set to false  and so it can be stolen easily in case of XSS vulnerability
        

        By default setcookie and setrawcookie functions set httpOnly flag to false (the seventh argument) and so cookies can be stolen easily in case of XSS vulnerability:

        $value = "sensitive data";
        setcookie($name, $value, $expire, $path, $domain, true); // Sensitive: a sensitive cookie is created with the httponly flag  (the seventh argument) not defined (by default set to false)
        setrawcookie($name, $value, $expire, $path, $domain, true); // Sensitive: a sensitive cookie is created with the httponly flag (the seventh argument) not defined  (by default set to false)
        

        Compliant Solution

        session.cookie_httponly = 1; // Compliant: the sensitive cookie is protected against theft thanks (cookie_httponly=1)
        
        session_set_cookie_params($lifetime, $path, $domain, true, true); // Compliant: the sensitive cookie is protected against theft thanks to the fifth argument set to true (HttpOnly=true)
        
        $value = "sensitive data";
        setcookie($name, $value, $expire, $path, $domain, true, true); // Compliant: the sensitive cookie is protected against theft thanks to the seventh argument set to true (HttpOnly=true)
        setrawcookie($name, $value, $expire, $path, $domain, true, true); // Compliant: the sensitive cookie is protected against theft thanks to the seventh argument set to true (HttpOnly=true)
        

        See

        • OWASP - Top 10 2021 Category A5 - Security Misconfiguration
        • OWASP HttpOnly
        • OWASP - Top 10 2017 Category A7 - Cross-Site Scripting (XSS)
        • CWE - CWE-1004 - Sensitive Cookie Without 'HttpOnly' Flag
        • Derived from FindSecBugs rule HTTPONLY_COOKIE
        • STIG Viewer - Application Security and Development: V-222575 - The application must set the HTTPOnly flag on session cookies.
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use